-
Notifications
You must be signed in to change notification settings - Fork 706
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
revert to using a bundle of components to install PyQt5, rather than a bundle of extensions #13336
revert to using a bundle of components to install PyQt5, rather than a bundle of extensions #13336
Conversation
Test report by @branfosj |
@boegelbot please test @ generoso |
@boegel: Request for testing this PR well received on generoso PR test command '
Test results coming soon (I hope)... - notification for comment with ID 873455948 processed Message to humans: this is just bookkeeping information for me, |
Even with easybuilders/easybuild-framework#3762 merged (which fixes easybuilders/easybuild-framework#3710), reverting back to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Test report by @boegel |
Going in, thanks @branfosj! |
Test report by @boegelbot |
(created using
eb --new-pr
)Partially reverts the changes in #13253 for PyQt5.
Error:
PyQt5 install the different parts as components using a variety of EasyBlocks. Switching to
exts_list
stops the custom easyblock definition from being used and installs each as aPythonPackage
and that causes the PyQt5 component to fail as it uses a different install method.See easybuilders/easybuild-framework#3710 for the
exts_list
not honouringeasyblock
.I've checked through #13253 and this is the only case I could see where this change was made.